fix(lakebase): Update instructions for manually obtaining LAKEBASE_ENDPOINT#121
Merged
fix(lakebase): Update instructions for manually obtaining LAKEBASE_ENDPOINT#121
LAKEBASE_ENDPOINT#121Conversation
LAKEBASE_ENDPOINT
d4b0eee to
df48d32
Compare
MarioCadenas
approved these changes
Feb 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The initial instructions were wrong - the
LAKEBASE_ENDPOINTis not as predictable as it was stated. This PR shows the correct way to obtain it.Related instruction: https://docs.google.com/document/d/13WTwiqCmfDlxzBRs6uOlGBtJ3f0qENw4uakK4cfkbg8/edit?tab=t.vwb898fzy8pk#heading=h.hycu8yx3j9n5
Related discussion: https://databricks.slack.com/archives/C0A2344S7U7/p1771508954452079